|
|
Fintraffic ANS is responsible for providing air traffic services in Finland with the exception of the Flight Information Zones surrounding Mikkeli and Seinäjoki instrument aerodromes during the service hours of the ATS units of the aforementioned aerodromes. Contact information in para 6.
|
The services are provided, in general, in accordance with the provisions contained in the following ICAO documents:
|
Significant differences between national and international rules and procedures are given in section GEN 1.7.
|
-
Annex 2 Rules of the Air
-
Annex 11 Air Traffic Services
-
Doc 4444 Procedures for Air Navigation Services - Rules of the Air and Air Traffic Services (PANS-RAC)
-
Doc 8168 Procedures for Air Navigation Services - Aircraft Operations (PANS-OPS)
-
Doc 7030 Regional Supplementary Procedures
|
|
The Helsinki flight information region (HELSINKI FIR) comprising the Finnish territorial airspace and the airspace over the adjacent high seas.
|
Areas within the Finnish flight information region in the vicinity of State border where provision of Air Traffic Services has for traffic flow reasons been delegated to Swedish or Norwegian ATS authority are prescribed in section ENR 2.1 and ENRC.
|
|
The following types of services are provided:
-
Area control service (ACC)
-
Approach control service (APP)
-
Aerodrome control service (TWR)
-
Alerting service (ALRS)
-
Flight Information Service (FIS)
-
Aerodrome Flight Information Service (AFIS)
|
Air traffic control service can be performed with radar. Additionally Automatic Terminal Information Service (ATIS) is in use in Finland.
|
The Finnish ATS system
, including the Airspace Classification, the division of airspace and hours of establishment are given in ENR 1.4. The units providing services within Finnish airspace is given in sections ENR 2 and AD 2.
|
Radar services and procedures
are described in ENR 1.6.
|
3.1 Operations at Finnish airports where Aerodrome Flight Information Service (AFIS) is provided
|
|
Aerodrome Flight Information Service (AFIS) is a part of ATS system in Finland and the units providing this service are called AFIS units. AFIS service, provided by trained Flight Information Officers, is available at those instrument aerodromes in Finland, where the type and density of the air traffic does not require controlled airspace and ATC. The purpose of AFIS is to provide information necessary for the safe and efficient conduct of flight operations in the vicinity of the aerodrome and in the manoeuvring area. It shall be noted, that the pilot-in-command is - on the basis of the Rules of the Air, the information received and the use of their own judgment - responsible to maintain safe distance to other traffic as well as to report own intentions. In terms of the use of equipment serving the aerodrome as well as the control of vehicle traffic, the procedures are similar to those applied at airports where ATC is provided.
|
3.1.2. Area of responsibility
|
The area of responsibility of the appropriate AFIS unit comprises the Flight Information Zone (FIZ) established around the aerodrome as well as the manoeuvring area. For lateral and vertical limits of the FIZ, see section AD 2. Airspace class for Flight Information Zone is G and it is defined to be radio mandatory zone (RMZ).
|
Note 1: At some AFIS aerodromes, ATC service may at times be provided instead of the AFIS service. This arrangement can be either permanent (AIP, AD 2) or temporary (AIP SUP). The information concerning the operational hours and the status of the service are given in AIS publications.
|
Note 2: A flight plan shall be submitted for any flight intended to be operated within a Flight Information Zone during its activity time (REF SERA.4001 1b) 3). The flight plan shall contain the items given in SERA.4005 a) 1) - 14) and in addition the name of the pilot in command.
|
Note 3: Two-way radio communication is required within the Flight Information Zone, REF AIP, ENR 1.4.
|
Note 4: Exemptions from the two-way radio communication requirement may be granted by the AFIS unit for an individual flight intended to the Flight Information Zone (REF SERA. 6005 a).
|
Note 5: Provisions concerning the use of VFR arrival / departing routes, reporting points and altitudes are given in section ENR 1.5.
|
3.1.3. Duties and functions of AFIS unit
|
Note: These procedures are in force during the operational hours of appropriate AFIS unit.
|
The AFIS unit:
-
provides the aircraft operating within the area of responsibility traffic information and other essential information (meteorological information, aerodrome conditions, etc.),
-
monitors the functionality of the facilities serving the aerodrome,
-
relays air traffic control clearances and route information issued by ATC units (see para 3.1.3.1 below),
-
notifies runway in use for take-off and landing (see para 3.1.3.2 below),
-
provides aircraft parking instructions if necessary,
-
controls vehicle traffic,
-
provides alerting service.
|
3.1.3.1. Route clearances and route information
|
The AFIS unit requests the ACC for a route clearance / route information to be forwarded to the aircraft in the following cases:
|
-
Route clearance: for IFR/VFR aircraft flying from Flight Information Zone into the controlled airspace.
|
-
Route information: IFR flight from Flight Information Zone into the uncontrolled airspace (airspace class G), see also the note below.
|
Note: The pilot-in-command shall be aware of that VFR aircraft operating in uncontrolled airspace do not have to report their flights and no two-way radio communication requirements exist so ATS does not necessarily be aware of these flights.
|
|
The term ‘Runway in use’ indicates the runway that at the particular time is considered by the AFIS unit to be the most suitable for the aircraft performing take-off or landing.
|
Note 1: An aircraft is assumed to take-off and land into the wind unless safety and traffic situation determine that a different direction is preferable. When determining the runway in use the AFIS unit takes into account among others the following: the surface wind, traffic circuits, local weather conditions and environmental restrictions.
|
Note 2: The pilot-in-command may use, traffic situation and prevailing circumstances permitting, other than runway in use after reporting this to the AFIS unit.
|
|
|
When an aircraft aloft can not be informed about a danger by any other means, the AFIS unit may use the following light signals for the purpose:
|
-
Red flashes (by lamp) - the aerodrome is dangerous
-
Red pyrotechnics (if available) - landing is not safe until further.
|
The light signals issued by the AFIS unit must be considered as warnings; the pilot bears the responsibility for any action due to the situation.
|
3.1.3.3.2. Visual ground signals
|
The visual ground signals according to Addition 1, para 3.2 to the Rules of the Air may be used at an AFIS aerodrome except the signal 3.2.5 ‘Direction of departure and landing’.
|
3.1.4. Operation of the aircraft
|
|
3.1.4.1. Departing aircraft
|
Departing aircraft shall report the AFIS unit about:
-
Intention to taxi for take-off. Turbine aircraft shall also report their readiness to start-up (see also para 3.1.4.5 below).
-
Intention to taxi for departure.
-
Selection of the runway; selection of a possible taxiholding position.
-
The planned route or the flight track and a possible intention to make a right turn.
|
Note: According to The Rules of the Air, an aircraft may make turns to the right after take-off and when approaching for a landing at an aerodrome where Aerodrome Flight Information is available providing that this can be done without hazard to other air traffic and the intention to turn right is reported to the AFIS unit.
|
-
Readiness for take-off (see also paras 3.1.4.6 and 3.1.4.7 below).
|
Note: AFIS-unit reports “No reported traffic RWYxx” Indicating that the runway is free for take-off.
|
-
Taxiing to the runway for take-off.
-
Leaving the Flight Information Zone (FIZ).
-
Any action or intention which may affect other traffic.
|
3.1.4.2. Arriving aircraft
|
An arriving aircraft shall report the AFIS unit about:
|
-
Its position, flying altitude and the estimated time of arrival to the aerodrome or above a navigation aid of the FIZ. This information must be given, at the latest, when arriving over the border of the FIZ or over a reporting point given in the approach chart.
|
Note: Initial contact should be established early enough to allow the AFIS unit to provide necessary traffic information. This is essential in cases where the FPL for operating within the FIZ is submitted in flight. To use of VFR reporting points and routes, see section ENR 1.5.
|
-
Runway selected and, if the flight is operated according to IFR, the approach procedure selected.
-
Any intention to use a right-hand circuit.
-
Arrival in the holding pattern and leaving it.
-
Commencing the approach procedure or entering the circuit.
-
Passing the IAF and the FAF or outer marker during an instrument approach.
-
Turn to base leg or to final.
|
Note: AFIS-unit reports “No reported traffic RWYxx” Indicating that the runway is free for landing.
|
-
Taxiing to the apron or parking area after the landing.
-
Missed approach and the intentions following.
-
Any other action, movement or intention, that may affect other air traffic.
|
3.1.4.3. Aircraft crossing the FIZ
|
Any other aircraft entering the FIZ and not having the intention to land at the aerodrome, shall report the AFIS unit about:
|
-
Position and flying altitude.
-
Route, intentions and flying altitude while flying in the FIZ and possible changes.
-
Estimated time of entering the FIZ, the navigational aid or over the aerodrome, actual over flying time of above mentioned points and time of leaving the FIZ.
|
3.1.4.4. Aircraft moving on the manouevring area
|
An aircraft, which operates in the manoeuvring area of the aerodrome and the operation is not connected with a landing or take-off, shall report its intentions to the AFIS unit.
|
|
When a departing turbine-engined IFR aircraft requests to be ready for start-up, the AFIS unit:
|
-
Reports factors related to start-up (other traffic, aerodrome conditions, ATFCM restrictions) which may be influential in start-up, after which the pilot-in-command starts-up at his / her own discretion.
|
3.1.4.6. Holding before a take-off
|
When, due to other traffic, an immediate take-off is not possible, a departing aircraft shall hold:
|
-
At a taxi-holding position if this has been defined and the markings are visible, or
-
Otherwise at a distance of at least:
-
30 metres from the runway edge, where runway length is less than 900 metres, or
-
50 metres from the runway edge, where runway length is 900 metres or more.
|
|
In general, the take-offs are performed in the order which the aircraft have reported being ready. This order may, however, be altered if required by traffic situation or by mutual agreement of the pilots.
|
3.1.5. Aerial sporting and recreational activities
|
In order to allow flexible air traffic and to provide efficient aerodrome flight information service the operators of aerial sporting and recreational activities (parachute jumping activity, balloon flights, model flying, etc.) should contact the AFIS unit as early as possible to clarify and agree on necessary procedures.
|
4 CO-ORDINATION BETWEEN THE OPERATOR AND ATS
|
|
5 MINIMUM FLIGHT ALTITUDE
|
Published minimum altitudes do not contain correction for low temperature effect. These altitudes are for instance:
|
-
area minimum altitude (AMA)
-
obstacle clearance altitude (OCA)
-
minimum obstacle clearance altitudes (MOCA) for departure, arrival or approach procedure and ATS route segments
-
minimum sector altitude (MSA)
-
surveillance minimum altitude area (SMAA) minimum altitudes
|
In case ATC is vectoring IFR flight and when giving a direct routing which takes the aircraft off an ATS route, the controller will issue clearances such that the prescribed obstacle clearance will exist at all times until the aircraft reaches the point where the pilot will resume own navigation. Such a clearance will include correction for low temperature effect when the required correction exceeds 20% of the prescribed minimum obstacle clearance.
|
If correction for low temperature effect is taken into account by the controller, given clearance includes "TEMPERATURE CORRECTED BY ATC".
|
Note: If given altitude clearance (higher than the minimum altitude) guarantees minimum obstacle clearance as is, correction is not added to that altitude.
|
In other cases, the pilot-in-command is responsible for applying the appropriate correction for the cold temperature effect.
|
|
HELSINKI ACC
|
|
Helsingin aluelennonjohto / Area Control Centre Helsinki PL 157 FI-01531 VANTAA Finland
|
+358 3 386 5171
+358 3 386 5172
|
|
|
EFINZFZX
EFINZQZX
|
|
AIR NAVIGATION SERVICES
|
|
Fintraffic ANS PL 157 FI-01531 VANTAA
|
+358 20 4284 000
|
|
ans@fintraffic.fi
|
EFHKYAYA
|
https://www.fintraffic.fi/en/ans/general-terms-air-navigation-services
https://www.fintraffic.fi/fi/ans/palveluehdot
|
ENONTEKIÖ ATS
|
EFET
|
Hetantie 775, 99400 Enontekiö
|
+358 16 554 8420
|
|
ansefetats@fintraffic.fi
|
|
|
HALLI ATS
|
EFHA
|
Halinkankaantie 120 35600 HALLI
|
+358 3 532 0071
|
|
ansefhaats@fintraffic.fi
|
|
|
HELSINKI-VANTAA ATS
|
EFHK
|
PL 157 FI-01531 VANTAA
|
+358 9 6151 3325
|
|
efhk.ats@fintraffic.fi
|
|
|
IVALO ATS
|
EFIV
|
Lentokentäntie 290, 99800 Ivalo
|
+358 16 675 8620
+358 29 439 8212
|
|
ansefivats@fintraffic.fi
|
|
|
JOENSUU ATS
|
EFJO
|
Lentoasemantie 30, 80140 Joensuu
|
+358 13 611 7020
|
|
ansefjoats@fintraffic.fi
|
|
|
JYVÄSKYLÄ ATS
|
EFJY
|
Lentoasemantie 70, 41160 Tikkakoski
|
+358 14 445 5880
|
|
ansefjyats@fintraffic.fi
|
|
|
KAJAANI ATS
|
EFKI
|
Lentokentäntie 7, 87850 Paltaniemi
|
+358 8 689 7520
|
|
ansefkiats@fintraffic.fi
|
|
|
KEMI-TORNIO ATS
|
EFKE
|
Lentokentäntie 75, 94500 Lautiosaari
|
+358 16 211 8720
|
|
ansefkeats@fintraffic.fi
|
|
|
KITTILÄ ATS
|
EFKT
|
Levintie 259, 99100 Kittilä
|
+358 16 366 8920
|
|
ansefktats@fintraffic.fi
|
|
|
KOKKOLA-PIETARSAARI ATS
|
EFKK
|
Lentäjäntie 162, 68500 Kruunupyy
|
+358 6 869 6820
|
|
ansefkkats@fintraffic.fi
|
|
|
KUOPIO ATS
|
EFKU
|
Lentokentäntie 275, 70900 Toivala
|
+358 17 580 7261
|
|
ansefkuats@fintraffic.fi
|
|
|
KUUSAMO ATS
|
EFKS
|
Lentokentäntie, 93600 Kuusamo
|
+358 8 851 8820
|
|
ansefksats@fintraffic.fi
|
|
|
LAPPEENRANTA ATS
|
EFLP
|
Lentokentäntie 21, 53600 Lappeenranta
|
+358 5 680 6321
|
|
anseflpats@fintraffic.fi
|
|
|
MARIEHAMN ATS
|
EFMA
|
Flygfältsvägen 67 22120 Mariehamn Åland, Finland
|
+358 18 634 420
|
|
ansefmaats@fintraffic.fi
|
|
|
MIKKELI ATS
|
EFMI
|
|
+358 15 366 427
|
|
|
|
|
OULU ATS
|
EFOU
|
Lentokentäntie 720, 90410 Oulu
|
+358 8 880 7804
|
|
ansefouats@fintraffic.fi
|
|
|
PORI ATS
|
EFPO
|
Lentoasemantie 1, 28500 Pori
|
+358 2 6100 6050
|
|
ansefpoats@fintraffic.fi
|
|
|
ROVANIEMI ATS
|
EFRO
|
Lentokentäntie, 96930 Rovaniemi
|
+358 16 363 6612
|
|
ansefroats@fintraffic.fi
|
|
|
SAVONLINNA ATS
|
EFSA
|
Lentoasemantie 50 57310 Savonlinna
|
+358 15 411 8120
|
|
ansefsaats@fintraffic.fi
|
|
|
SEINÄJOKI ATS
|
EFSI
|
|
+358 6 421 9620
|
|
|
|
|
TAMPERE-PIRKKALA ATS
|
EFTP
|
Tornikaari 40, 33960 Pirkkala
|
+358 3 383 5433
|
|
anseftpats@fintraffic.fi
|
|
|
TURKU ATS
|
EFTU
|
Lentoasemantie 150, 20360 Turku
|
+358 2 415 4801
|
|
anseftuats@fintraffic.fi
|
|
|
UTTI ATS
|
EFUT
|
Lentoportintie 87, 45410 Utti
|
+358 5 340 8320
|
|
ansefutats@fintraffic.fi
|
|
|
VAASA ATS
|
EFVA
|
Lentokentäntie 174, 65380 Vaasa
|
+358 6 212 6120
|
|
ansefvaats@fintraffic.fi
|
|
|
|